Centralized control SIMD processor having different priority levels set for each data transfer request type and successively repeating the servicing of data transfer request in a predetermined order

ABSTRACT

Features which support conditional execution and sequencing are employed in concert with a centralized-control, single-instruction, multiple data integrated video signal processor, thus adapting efficiently to the high degree of parallelism inherent in this type of video signal processing systems. A three-level prioritization scheme is used to handle the input/output data stream to improve the throughput of the processor, including provisions for distinguishing between same-priority events occurring at different times, and ensuring that in such cases the requested operations occur in the same temporal order as the respective requests.

This application is a continuation of U.S. Ser. No. 07/980,392, filed on Nov. 23, 1993, now abandoned, which in turn is a divisional of application Ser. No. 07/926,742, filed on Aug. 6, 1992, now abandoned, which was a continuation-in-part of U.S. Ser. No. 07/782,332, filed Oct. 24, 1991, and now U.S. Pat. No. 5,361,370.

BACKGROUND OF THE INVENTION

1) Field of the Invention

This invention relates to the field of video signal processing, and, in particular, to video signal processing using an architecture having a plurality of parallel execution units.

2) Background Art

It is well known in the prior art to use multiple-instruction multiple-data systems for video signal processing. In a multiple-instruction multiple-data execution of an algorithm each processor of the video signal processor may be assigned a different block of image data to transform. Because each processor of a multiple-instruction multiple-data system executes its own instruction stream, it is often difficult to determine when individual processors have completed their assigned tasks. Therefore, a software synchronization barrier may be used to prevent any processors from proceeding until all processors in the system reach the same point. However it is sometimes difficult to determine where synchronization barriers are required. If a necessary barrier is omitted by a user then the resulting code may be nondeterministic and re-execution of the code on the same data may yield different results.

An alternate architecture known in the prior art is single-instruction multiple-data architecture. Single-instruction, multiple-data is a restricted style of parallel processing lying somewhere between traditional sequential execution and multiple-instruction multiple-data architecture having interconnected collections of independent processors. In the single-instruction, multiple-data model each of the processing elements, or datapaths, of an array of processing elements or datapaths executes the same instruction in lock-step synchronism. Parallelism is obtained by having each datapath perform the same operation on a different set of data. In contrast to the multiple-instruction, multiple-data architecture, only one program must be developed and executed.

Referring now to FIG. 1, there is shown prior art single-instruction multiple-data architecture 100. A conventional single-instruction multiple-data system, such as architecture 100, comprises a controller 112, a global memory 126 and execution datapaths 118a-n. A respective local memory 120a-n may be provided within each execution datapath 118a-n. Single-instruction multiple-data architecture 100 performs as a family of video signal processors 118a-n united by a single programming model.

Single-instruction multiple-data architecture 100 may be scaled to an arbitrary number n of execution datapaths 118a-n provided that all execution datapaths 118a-n synchronously execute the same instructions in parallel. In the optimum case, the throughput of single-instruction multiple-data architecture 100 may theoretically be n times the throughput of a uniprocessor when the n execution datapaths 118a-n operate synchronously with each other. Thus, in the optimum case, the execution time of an application may be reduced in direct proportion to the number n of execution datapaths 118a-n provided within single-instruction multiple-data architecture 100. However, because of overhead in the use of execution datapaths 118a-n, this optimum is never reached.

Architecture such as single-instruction multiple-data architecture 100 works best when executing an algorithm which repeats the same sequence of operations on several independent sets of highly parallel data. For example, for a typical image transform in the field of video image processing, there are no data dependencies among the various block transforms. Each block transform may be computed independently of the others.

Thus the same sequence of instructions from instruction memory 124 may be executed in each execution datapath 118a-n. These same instructions are applied to all execution datapaths 118a-n by way of instruction broadcast line 116 and execution may be independent of the data processed in each execution datapath 118a-n. However, this is true only when there are no data-dependent branches in the sequence of instructions. When data-dependent branches occur, the data tested by the branch will, in general, have different values in each datapath. It will therefore be necessary for some datapaths 118a-n to execute the subsequent instruction and other datapaths 118a-n to not execute the subsequent instruction. For example, the program fragment of Table I clips a value v between a lower limit and an upper limit:

                  TABLE I                                                          ______________________________________                                                  local v;                                                                       . . .                                                                          v = expression                                                                 if (v > UPPER.sub.-- LIMIT)                                                       v = UPPER.sub.-- LIMIT;                                                     if (v < LOWER.sub.-- LIMIT)                                                       v = LOWER.sub.-- LIMIT;                                            ______________________________________                                    

The value being clipped, v, is local to each execution datapath 118a-n. Thus, in general, each execution datapath 118a-n of single-instruction multiple-data architecture 100 executing the program fragment of Table I may have a different value for v. In some execution datapaths 118a-n the value of v may exceed the upper limit, and in others v may be below the lower limit. Other execution datapaths 118a-n may have values that are within range. However the execution model of single-instruction multiple-data architecture 100 requires that a single identical instruction sequence be executed in all execution datapaths 118a-n.

Thus some execution datapaths 118a-n may be required to idle while other execution datapaths 118a-n perform the conditional sequence of Table I. Furthermore, even if no execution datapaths 118a-n of single-instruction multiple-data architecture 100 are required to execute the conditional sequence of the program fragment of Table I, all execution datapaths 118a-n would be required to idle during the time of the conditional sequence.

Another problem with systems such as prior art single-instruction multiple-data architecture 100 is in the area of input/output processing. This problem arises due to the very large bandwidth requirements associated with this type of architecture. Even in conventional uniprocessor architecture a single block read instruction may take a long period of time to process because memory blocks may comprise a large amount of data in video image processing applications. However, this problem is compounded when there is a block transfer for each enabled execution datapath 118a-n of architecture 100 and datapaths 118a-n must compete for access to global memory 126. For example, arbitration overhead may be very time consuming. This is a problem particularly in video processing because of the large amount of data which must be processed in video applications.

The alternative of providing each execution datapath 118a-n with independent access to external memory 126 is impractical for semiconductor implementation. Furthermore, this alternative restricts the programming model so that data is not shared between datapaths 118a-n. Thus further inefficiency results due to the suspension of processing of instructions until all the block reads are completed. This may be seen in the discrete cosine transform image kernel of Table II:

                  TABLE II                                                         ______________________________________                                         for (i = 0; i < NUMBEROFBLOCKS; i = i + 4) {                                     k = i + THIS.sub.-- DP.sub.-- NUMBER;                                          read.sub.-- block(original.sub.-- image[k],temp.sub.-- block);                 DCT.sub.-- block(temp.sub.-- block);                                           write.sub.-- block(xform.sub.-- image[k], temp.sub.-- block);                };                                                                             ______________________________________                                    

The read₋₋ block and write₋₋ block routines of the instruction sequence of Table II must be suspensive. Each must be completed before the next operation in the kernel is performed. For example, read₋₋ block fills temp₋₋ block in local memory 120a-n with all of its local values. These local values are then used by DCT block to perform a discrete cosine transform upon the data in temp₋₋ block. Execution of the discrete cosine transform must wait for all of the reads of the read₋₋ block command of all execution datapaths 118a-n to be completed. Only then can the DCT₋₋ block and write₋₋ block occur. Thus, by the ordering rules above, read₋₋ block must be completed before the write₋₋ block is processed, or the DCT₋₋ block is executed.

Referring now to FIG. 2, there is shown processing/memory time line 200. The requirements imposed by the ordering rules within single-instruction multiple data architecture 100 result in the sequentialization of memory transactions and processing as schematically illustrated by processing/memory time line 200. In time line 200, memory read₋₋ block time segment 202 of execution datapath 118a-n must be completed before processing of DCT₋₋ block time segment 204 may begin. Processing DCT₋₋ block time segment 204 must be completed before memory write₋₋ block time segment 206 may begin. Only when memory write₋₋ block time segment 206 of a execution datapath 118a-n is complete, can memory read block₋₋ time segment 208 of a execution datapath 118a-n begin. Execution and access by second execution datapath 118a-n is sequentialized as described for the first.

This problem occurs in high performance disk input/output as well. In a typical disk input/output operation an application may require a transfer from disk while continuing to process. When the data from disk are actually needed, the application may synchronize on the completion of the transfer. Often, such an application is designed to be a multibuffered program. In this type of multibuffered program, data from one buffer is processed while the other buffer is being filled or emptied by a concurrent disk transfer. In a well designed system the input/output time is completely hidden. If not, the execution core of single-instruction multiple-data architecture 100 is waitstated until the data becomes available. This causes further degrading of the performance of the single-instruction multiple-data architecture 100.

SUMMARY OF THE INVENTION

All transfer between the local memory and the global memory take place using one dedicated port of the local memory. The transfers are scheduled and controlled by a common unit called the block transfer controller. The block transfer controller, along with the dedicated port of the dual ported local memory, permit each access to global memory by a datapath to be overlapped with its instruction processing. This usually avoids stalling the processor.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a block diagram representation of a prior art single-instruction multiple-data architecture suitable for processing highly parallel data such as data representative of video images;

FIGS. 2 shows a processing/memory time line for the image processing architecture of FIG. 1;

FIG. 3 shows the single-instruction multiple-data architecture image processor of the present invention;

FIGS. 4A, 4B, 4C and 4D show execution mask stacks;

FIG. 5 shows a processing/memory time line for the architecture of FIG. 3;

FIG. 6 shows a schematic representation of a memory-to-memory block transfer within the architecture of FIG. 3;

FIG. 7 shows a linked request list formed of command templates linked to each other and containing the parameters required to specify a memory-to-memory block transfer such as the transfer represented by FIG. 6;

FIG. 8 shows a simplified alternate embodiment of the single-instruction multiple-data architecture image processor of FIG. 3, wherein there is provided a four-execution datapath architecture;

FIG. 9 shows a block diagram representation of a system for performing internal scalar transfers between the datapaths of the single-instruction multiple-data image processor of FIG. 3;

FIG. 10 shows a block diagram representation of a statistical decoder for decoding variable length codes within the single-instruction multiple-data image processor of FIG. 3;

FIG. 11 shows a binary decoding tree for decoding variable length codes within the statistical decoder of FIG. 10.

FIG. 12 shows a block diagram representation of the block transfer controller priority algorithm of the present invention.

FIG. 13 shows a block diagram representation of a local priority algorithm within the block transfer controller priority algorithm of FIG. 12.

FIG. 14 shows a block diagram representation of a local priority algorithm within the block transfer controller priority algorithm of FIG.

FIG. 15 shows a block diagram representation of a local priority algorithm within the block transfer controller priority algorithm of FIG. 12.

FIG. 16 hows a block diagram representation of a transfer limiting algorithm for use within the block transfer controller priority algorithm of FIG. 12.

DETAILED DESCRIPTION OF THE INVENTION

Referring now to FIG. 3, there is shown single-instruction multiple-data architecture image processor 300 of the present invention. Single-instruction multiple-data image processor 300 is provided with execution masks and conditional control flow during conditional branches in order to provide more efficient use of computation time in execution datapaths 358a-n of image processor 300. Each of these two mechanisms addresses one of two distinct control needs within image processor 300.

Each execution datapath 358a-n of a single-instruction multiple-data image processor 300 is provided with a respective execution unit 360a-n and local memory 362a-n. Each execution unit 360a-n of execution datapath 358a-n is coupled to its respective local memory 362a-n by way of a respective local memory port 361a-n and to system memory 364 and global memory 66 by way of a respective global memory port 363a-n. Local memory ports 361a-n and global memory ports 363a-n, together, provide each execution datapath 358a-n with a dual port architecture to permit each execution unit 360a-n to access its respective local memory 362a-n simultaneously with data transfer between local memories 362a-n and memories 364, 366. It will be understood that within the dual port architecture of image processor 300, no execution unit 360a-n may directly access any local memory 362a-n except its own.

During execution of instructions, instruction sequence controller 352 of single-instruction multiple-data image processor 300 simultaneously applies the same instruction to every execution datapath 358a-n by way of broadcast instruction line 356. The instructions applied by sequence controller 352 are previously stored in either system memory 364 or global memory 366. The instructions received by sequence controller 352 are applied to sequence controller 352 by way of memory instruction line 356. Within image processor 300, conditional execution permits each datapath 358a-n to execute or not execute a particular issued instruction depending on the state of the local datapath condition flag. Hardware execution masks, residing within execution units 360a-n of image processor 300, permit individual datapaths 358a-n to turn off execution of a sequence of issued instructions for an arbitrary period of time. These two mechanisms permit efficient control of wait stating or idling of execution datapaths 360a-n within single-instruction multiple-data image processor 300, thereby permitting efficient use of execution datapaths 358a-n.

Control over whether an instruction issued by sequence controller 352 is executed or ignored by an individual execution datapath 358a-n is required for data-dependent computation in a single-instruction multiple-data architecture such as the architecture of image processor 300. It is required because each execution datapath 358a-n may have a different value when a test is performed as part of a conditional branch. Thus each execution datapath 358a-n within image processor 300 of the present invention is provided with individual datapath execution masks.

It is equally important to control the sequence of instructions provided by sequence controller 352 to execution datapaths 358a-n by way of broadcast instruction line 356. This control is essential for loops and may also be used to optimize data-dependent execution wherein no execution datapath 58a-n is required to execute a conditional sequence of instructions.

For the purpose of executing a conditional branch within image processing architecture 300, each datapath 358a-n tests the condition of a conditional branch and independently sets its own flags according to its own local determination. Signals representative of these flags are applied by each execution datapath 358a-n to instruction sequence controller 352 by way of flag signal lines 354a-n.

Rather than automatically wait-stating all execution datapaths 358a-n during a conditional, single-instruction multiple-data architecture 300 of the present invention uses the flag signals of flag lines 354 to apply a consensus rule. In the consensus rule of image processor 300, sequence controller 352 does not apply a conditionally executed instruction sequence to broadcast instruction line 356 unless flag lines 354 signal controller 352 that every execution datapath 358a-n requires the instruction sequence.

Both mechanisms, conditional execution and execution masks may be used to implement the conditional execution within image processor 300, when some but not all datapaths 358a-n require it. Of these two mechanisms, execution masks EM are more the general. The execution mask flag is appended to the normal set of local arithmetic condition code flags within each execution unit 360a-n. When an execution mask flag EM is set within an execution unit 360a-n of execution datapaths 358a-n and sequence controller 352 applies the conditional sequence to broadcast instruction line 356, each execution unit 360a-n having its execution mask flag EM set ignores the instructions.

The only exceptions to instructions being ignored by execution datapath 358a-n within image processor 300 when an execution mask flag EM is set are 1) the instruction which restores the state of the previous execution mask flag, and 2) those instructions which unconditionally modify the execution mask flag EM. These instructions are executed by all execution unit 358a-n even if the execution mask flag EM within a datapath 358a-n is set. Thus, if the execution mask flag EM is set in a selected execution unit 360a-n, instructions from instruction sequence controller 352 are ignored by the selected execution unit 360a-n.

It is then possible to encode a conditional thresholding program fragment within single-instruction multiple-data architecture image processor 300 using execution masks EM. This thresholding program is set forth in the instruction sequence of Table III. The instruction sequence of Table III is adapted to perform, within image processor 300, the clipping operation performed by the instruction sequence of Table I within prior art architecture 100. In this instruction sequence a local value v is constrained within a range between the values LOWER₋₋ LIMIT and UPPER₋₋ LIMIT.

                  TABLE III                                                        ______________________________________                                         CMP v,UPPER.sub.-- LIMIT;                                                                         compare and set flags on all                                                   execution datapaths 358a-n                                  MOV EM,LE;         set execution masks EM on                                                      execution datapaths 358a-n                                                     with less than or equal flag                                                   set                                                         MOV v,UPPER.sub.-- LIMIT;                                                                         update v only on execution                                                     datapaths 358a-n with                                                          greater than flags set                                      MOV EM,0;          every execution datapath                                                       358a-n executes                                                                unconditional reset of EMs,                                                    activating all datapaths                                                       358a-n                                                      CMP v,LOWER.sub.-- LIMIT;                                                                         compare and set flags on all                                                   execution datapaths 358a-n                                  MOV EM,GE;         set EM on datapaths 358a-n                                                     with greater than or equal                                                     flag set                                                    MOV v,LOWER.sub.-- LIMIT;                                                                         update v on execution                                                          datapaths 358a-n with less                                                     than flag set                                               MOV EM,0;          reenable every execution                                                       datapath 358a-n                                             ______________________________________                                    

The first instruction of Table III, executed by all execution datapaths 358a-n of single-instruction multiple-data architecture image processor 300, compares the local value of v for each execution datapath 358a-n against the same upper threshold UPPER₋₋ LIMIT. The MOV EM,LE instruction of Table III is then executed by all execution datapaths 358a-n of image processor 300. A respective execution mask flag EM is thereby determined within each execution datapath 358a-n according to the comparison of the local v. Each execution datapath 358a-n is thus provided with a respective setting of the flag EM in its individual flag register.

In execution datapaths 358a-n where the less-than-or-equal condition is met, the MOV EM,LE instruction results in the execution mask flag EM being set to the value one. Execution datapaths 358a-n wherein the execution mask flag EM is set to the value one are disabled. These disabled execution datapaths 358a-n ignore instructions applied by sequence controller 352 by way of broadcast instruction line 356. In particular, execution datapaths 358a-n having their execution mask flag EM set to one by the MOV EM,LE instruction of Table III ignore the MOV v,UPPER₋₋ LIMIT instruction. In execution datapaths 358a-n where the less-then-or-equal condition is not met, the execution mask flag is set to the value zero. These datapaths 358a-n execute the MOV v, UPPER₋₋ LIMIT instruction, thereby clipping any local values of v which were greater than UPPER₋₋ LIMIT.

Thus the MOV v,UPPER₋₋ LIMIT, is executed only by those execution datapaths 358a-n where the greater-than condition was met in the first instruction of Table III and the execution mask flag EM has the value zero. The fourth instruction of Table III, MOV EM,0, unconditionally resets the execution mask flag EM of all execution datapaths 358a-n of image processor 300 including those execution datapaths 358a-n wherein the execution mask flag EM was set by the CMP v,UPPER₋₋ LIMIT instruction. Thus the update of the value of v within the sequence of Table III occurs only in those execution datapaths 360a-n in which it is required and execution mask flags EM of all execution units 360a-n are reset to zero for the next compare instruction.

The example of Table III may be simplified using conditional execution as illustrated by the instruction sequence of Table IV.

                  TABLE IV                                                         ______________________________________                                                 CMP v,UPPER.sub.-- LIMIT                                                                        Compare local values                                                           of v and set all                                                               flags in all                                                                   execution datapaths                                                            358a-n                                                IF (GT):                                                                               MOV v,UPPER.sub.-- LIMIT                                                                        Executed only by                                                               execution datapaths                                                            358a-n where local                                                             values of v exceed                                                             UPPER.sub.-- LIMIT.                                           CMP v,LOWER.sub.-- LIMIT                                                                        Set all flags on all                                                           execution datapaths                                                            358a-n and compare.                                   IF (LT):                                                                               MOV v,LOWER.sub.-- LIMIT                                                                        Executed only by                                                               execution datapaths                                                            358a-n where local                                                             values of v are less                                                           than LOWER.sub.-- LIMIT.                              ______________________________________                                    

Conditional execution within image processor 300 permits every instruction to be executed by each datapath 358a-n based on the data-dependent condition code local to the individual datapath 358a-n. The conditional execution feature of image processor 300 is thus more efficient than prior art architecture, such as prior art architecture 100. However, the method described does not allow for nesting of data dependent execution when using execution masks EM. In these nested execution cases conditional execution may still be used for improved efficiency in the innermost of the nested data dependencies. The two mechanisms are therefore complementary and may be used together to achieve maximum efficiency.

In order to permit nesting, the execution mask is generalized to a stack. In the preferred embodiment of image processing system 300, the execution mask stacks are respective hardware stacks 359a-n residing in each execution unit 358a-n. The push command pushes the local execution mask or condition code of an individual execution datapath 358a-n onto its individual execution mask stack. Push and pop operations are executed by all execution datapaths 358a-n, regardless of whether they are active.

In the case of an inactive datapath 358a-n, the condition code pushed onto the stack 359a-n has the value one, indicating that the inactive datapath 358a-n is off. The remaining active datapaths 358a-n execute the compare against UPPER₋₋ LIMIT. The subset of datapaths 358a-n not requiring a clip against UPPER₋₋ LIMIT are turned off by the next push operation. Following the clip, a pop restores the prior state and those datapaths 358a-n with clipping enabled are all reenabled for the test against LOWER₋₋ LIMIT. Following the similar clipping against LOWER₋₋ LIMIT, the final pop operation reenables all datapaths 358a-n. It is necessary for push and pop to execute in all datapaths 358a-n in order to insure the consistency of the execution mask stack 359a-n.

In the case of a nested conditional, a conditional sequence expression is executed only when some further condition is true. For example, in some applications a determination whether v is within range, similar to the determination of Table V, may be made only if the clipping routine is enabled. This is indicated when the variable enable₋₋ clipping is non-zero in the instruction sequence of Table V.

                  TABLE V                                                          ______________________________________                                                 local v;                                                                       . . .                                                                          v = expression}                                                                if (enable.sub.-- clipping) {                                                     if (v > UPPER.sub.-- LIMIT)                                                    v = UPPER.sub.-- LIMIT;                                                     if (v < LOWER.sub.-- LIMIT)                                                       v = LOWER.sub.-- LIMIT;                                                     }                                                                              . . .                                                                  ______________________________________                                    

However, when executing the instruction sequence of Table V it is not possible to merely compare enable₋₋ clipping in each execution datapath 358a-n and set the execution mask flag EM accordingly when a MOV EM,0 instruction corresponding to the upper limit test is executed. Because such a setting of the execution mask flag EM would be unconditional, all execution datapaths 358a-n would execute it. This would cause all execution datapaths 358a-n within image processor 300 to become enabled.

Thus, even execution datapaths 358a-n, where enable₋₋ clipping was false, would be enabled. Therefore, all execution datapaths 358a-n would perform the subsequent lower limit test, even those that should not perform any clipping of v at all because their clipping routine was not enabled. However, conditional execution and execution masks can both be used to efficiently implement an enabled clipping operation. Additionally, it may be implemented without the use of conditional execution. This is useful for illustrating the generality of the execution mask technique which may be applied to arbitrary levels of nesting.

Conditional execution and execution masks may both be used to efficiently implement the example with enabled clipping as shown in Table VI.

                  TABLE VI                                                         ______________________________________                                                 CMP ENABLE,0                                                                   MOV EM,EQ        Disable execution                                                              datapaths 358a-n                                                               where clipping is                                                              not enabled                                                   CMP v,UPPER.sub.-- LIMIT                                                                        Compare and set all                                                            flags on all                                                                   execution datapaths                                                            358a-n                                                IF (GT):                                                                               MOV v,UPPER.sub.-- LIMIT                                                                        Executed only by                                                               execution datapaths                                                            358a-n where local                                                             values of v exceed                                                             UPPER.sub.-- LIMIT                                            CMP v,LOWER.sub.-- LIMIT                                                                        Compare and set all                                                            flags on all                                                                   execution datapaths                                                            358a-n                                                IF (LT):                                                                               MOV v,LOWER.sub.-- LIMIT                                                                        Executed only by                                                               execution datapaths                                                            358a-n where local                                                             values of v are less                                                           than LOWER.sub.-- LIMIT                                       MOV EM,0         Reenable all                                                                   execution datapaths                                                            358a-n                                                ______________________________________                                    

This example can also be implemented without the use of conditional execution as shown in Table VII. This illustrates the generality of the execution mask technique which may be applied to arbitrary levels of nesting.

                  TABLE VII                                                        ______________________________________                                         CMP ENABLE,0                                                                   PUSH EM,EQ                                                                       CMP v,UPPER.sub.-- LIMIT                                                       PUSH EM,LE                                                                        MOV v,UPPER.sub.-- LIMIT                                                    POP                                                                            CMP v,LOWER.sub.-- LIMIT                                                       PUSH EM,GE                                                                        MOVE v,LOWER.sub.-- LIMIT                                                   POP                                                                          POP                                                                            ______________________________________                                    

Referring now to FIGS. 4A-D, there are shown execution mask stack maps 402, 404,406, and 408, representing execution mask stacks 359a-n. Stack maps 402, 404, 406, and 408 schematically illustrate portions of execution units 360a-n within execution datapath 358a-n of image processor 300. As previously described, in the preferred embodiment of execution units 360a-n, dedicated hardware is provided within execution units 360a-n to perform the functions of stacks 359a-n. Execution mask flag stack 359i of datapath 358x, where 1≦x≦n, contains y execution mask flags, where execution mask flag EMx.1 is the first execution mask pushed onto mask stack 359x, EMx.2 is the second mask pushed onto execution mask flag stack 359x, and so on.

In general, an expression that sets an execution mask flag EMx.y may be coded to work correctly in any nested conditional, such as the conditional in the instruction sequence of TABLE VI, by saving the state of execution mask flag EMx.y in a temporary location at the beginning of the expression and restoring it at the end. Execution mask flag stacks 359a-n are provided for this purpose within respective execution units 360a-n of datapaths 358a-n.

It will be understood by those skilled in the art that the index x identifies a particular execution datapath 358a-n having an execution mask stack 359x within execution unit 360x and that the index y represents the number of masks stacked in execution mask stack 359x. Thus single-instruction multiple-data image processor 300 of the present invention provides execution mask flag stacks 359a-n for sequentially storing and sequentially retrieving execution mask flags EMx.y within each execution unit 360a-n of each execution datapath 358a-n.

When the first instruction of the sequence of Table VII, CMP ENABLE,0, is executed, the equal flag of execution datapath 358a-n and the equal flag of execution datapath 358n are set because the user has defined them to be enabled. Execution masks EMa.1, EMb.1, and EMn.1, appear in mask stacks 359a,b,n respectively within execution units 360a,b,n when the next instruction, PUSH EM,EQ, is executed by datapaths 358a,b,n.

Because datapath 358a and datapath 358n of execution mask stack map 402 are enabled, execution mask EMa.1 in execution mask stack 359a and execution mask EMn.1 in execution mask flag stack 359n have a value of zero. This permits execution datapaths 358a,n to execute instructions from sequence controller 352. Execution mask EMb.1, the first mask in execution mask stack 359b, has the value one because the user has previously defined datapath 358b to be disabled. Because execution datapath 358b is disabled, it does not execute instructions from sequence controller 352.

The next instruction of the instruction sequence of Table VII, CMP v,UPPER₋₋ LIMIT, is a nested data dependency. It causes some datapaths 358a-n which execute it to set the LE flag according to the local value of v. Other datapaths 358a-n which execute this instruction do not set the LE flag. Furthermore, some datapaths 358a-n do not execute the instruction at all. For example, execution datapath 358b does not execute the instruction because the top most mask stacked in execution mask stack 359b, EMb.1, has a value of one. Execution datapath 358a and execution datapath 358n do execute the comparison instruction because their top most execution masks, EMa.1 and EMn.1, both have the value of zero.

When execution datapaths 358a,n execute the comparison and the instruction PUSH EMILE, they each push a new execution mask, EMa.2 and EMn.2. These new execution masks are stored in their respective execution mask stacks 359a,n of the new execution mask stack map 404. A further execution mask EMb.2, having the value one, appears on stack 359b within execution unit 360b of datapath 358b. Because datapath 358b is inactive the disabling execution mask is merely reproduced by the push operation.

For the purposes of illustration, consider the case wherein the results of the upper limit comparison are such that execution datapath 358a must clip its local value of v while the local value of v of execution datapath 358n is not above the range and does not require clipping. In this case execution mask flag EMa.2, pushed onto mask stack 359a, has the value of zero, and execution mask EMn.2, pushed onto mask stack 359n has the value one. Thus, during the execution of the next instruction, wherein the upper limit is moved to the local value of v, execution datapath 338a is active and performs the move, thereby clipping the value of v local to datapath 358a. During this instruction cycle execution datapaths b,n are inactive and do not perform the move, although they were inactivated at different points within the instruction sequence of TABLE VII.

During the execution of the next instruction, POP, execution masks EMa.2, EMb.2, and. EMn.2 are removed from mask stacks 359a,b,n respectively as shown in execution mask stack map 406. The top most execution mask in mask stack 359n, EMn.1, has a value of one as previously determined by the enable comparison. Thus, by stacking execution masks EMn.1 and EMn.2 within stack 359n of execution datapath 358n, execution of datapath 358n was disabled during a nested loop and reenabled at the end of the nested loop. More generally, all execution datapaths 358a-n within single instruction multiple data video processor architecture 300 are able to idle or inactivate according to local data dependencies during a nested loop. Upon leaving the nested loop, each execution datapath 358a-n may restore its execution mask status to its status prior to entering the loop. The POP instruction which follows then clears all execution masks EMi.1, as pushed onto execution mask stacks 359a-n by the PUSH instruction as shown in execution mask stack map 408.

It will be understood that the example of Table VII, as illustrated by execution mask stack maps 402, 404, 406, and 408, may occur embedded within a further instruction sequence (not shown). Instructions within the further instruction sequence may have pushed a plurality of flags onto mask stacks 359a-n previous to the first PUSH instruction of Table VII. Therefore the final POP instruction of Table VII may restore a previous execution mask status for execution datapaths 358a-n for further execution by image processor 300.

Each execution mask flag stack 359a-n within its respective execution datapath 358a-n thus provides automatic storage for execution mask flags EMx.y in image processor 300 of the present invention. In this method, execution mask flags EMx.y are pushed onto execution mask flag stacks 359a-n of execution datapaths 358a-n. When execution mask flags EMx.y are pushed onto stacks 359a-n, an operation may be performed by selected execution units 360a-n, and execution mask flags Emx.y may then be popped off stacks 359a-n. Stacks 359a-n containing execution masks EMx.y within each execution datapath 358a-n of single-instruction multiple-data architecture 300 may have any number of entries. For example, execution datapaths 358a-n of image processor 300 may be provided with stacks 359a-n having sixteen or thirty-two entries.

The execution mask discipline described thus far provides a way to control, within an individual execution datapath 358a-n, the conditional execution of an instruction issued by sequence controller 352 of single-instruction multiple-data architecture 300. However, this execution mask discipline does not provide a way to conditionally control the sequence of instructions issued by sequence controller 352 during a conditional branch. For example: ##EQU1## The following instruction sequence of Table VIII performs this operation.

                  TABLE VIII                                                       ______________________________________                                              MOV j,0;            initialize induction                                  L1:  CMP j,NUMBEROFBLOCKS;                                                                              variable test for                                                              end condition                                              JGE L2              exit if condition met by                                                       all active datapaths                                                           358a-n                                                     MOV EM,GE           turns off those datapaths                                                      358a-n                                                                         meeting exit condition                                     . . .                                                                          ADD j,4;            increment j                                                JMP L1;             go back for more                                      L2.                      finished                                              ______________________________________                                    

In the instruction sequence of Table VIII a copy of the local loop induction variable j exists in all execution datapaths 358a-n. The operation CMP j,NUMBEROFBLOCKS individually sets the execution mask flags EMx.y of each execution unit 360a-n according to the local value of j. Because all execution datapaths 358a-n initialize j to the same value of zero and perform the same operation, ADD j,4, upon j, the execution mask flags EM of all execution datapaths 358a-n should be identical.

Since each execution datapath 358a-n may have a different number of blocks to process, the value NUMBEROFBLOCKS may vary from one execution datapath 358a-n to another. The instruction sequence for the loop is executed only if at least one datapath has an index j less than NUMBEROFBLOCKS. Prior to executing the loop, those execution datapaths 358a-n Which meet the exit condition are turned off by MOV EM,GE. When only a single execution datapath 358a-n is enabled within image processor 300, the enabled execution datapath 358a-n behaves like a conventional uniprocessor.

The consensus rule of image processor 300 allows the easy coding of a conditional program fragment that may be jumped over by all execution datapaths 358a-n if no execution datapath 358a-n requires the execution of the fragment. For example, occasionally v is negative. A very complex calculation requiring a great deal of processing time is required within execution units 360a-n when v is negative. If the calculation required for a negative v is sequenced, even if no execution datapath 358a-n requires it, extremely inefficient use is made of the processing power within single-instruction multiple-data architecture 300. Therefore, using the consensus rule, sequence controller 352 does not apply the instructions required for a negative v to broadcast instruction line 356 for transmission to execution datapaths 358a-n if no datapath 358a-n is processing a v having a negative value.

It is important to note that the consensus rule is complete. The dual to branching if all execution datapaths 358a-n satisfy the condition code ("if all") is to branch if any execution datapath 358a-n satisfies the condition code ("if any"). It is illustrated below how the branch "if any" function may be implemented using the branch "if all" type of branch. The duals to all condition codes are included within single-instruction multiple data image processor 300 which makes the "if any" function simple to code.

As previously described, each execution datapath 358a-n within single-instruction multiple-data image processor 300 is equipped with large local memory 362a-n. Each execution unit 360a-n of each respective execution datapath 358a-n directly accesses its own local memory 362a-n by way of a respective dual port 361a-n or program port 361a-n. Each dual port 361a-n or local memory port 361a-n of image processor 300 is provided with an both A port and a B port. Different signals may be transmitted between each execution unit 360a-n and its local memory 362a-n simultaneously by way of the A and B ports under the control of the program being executed within execution units 360a-n. It will be understood that this transfer by way of local memory ports 361a-n is distinguished from transfers by way of transfer ports 363a-n under the control of block transfer controller 368.

It will be understood that this type of access to local memories 362a-n by execution units 360a-n involves writing of pointers only. Thus these operations are not actually random accessing of local memories 362a-n. This ability of block transfer controller 368 permits split phase transactions as shown in processing/memory time line 500. These split phase transactions are completely independent of instruction sequencer 352. Thus, block transfer controller 368 operates as a separate instruction engine not directly controlled by instruction sequence controller 352. This allows efficient access to memory for the instruction cache. It permits the cache to be filled quickly even if another block is getting instructions from external memory 364, 366. Therefore, block transfer controller 368 minimizes idling or wait stating of execution datapaths 358a-n while waiting for instructions.

It will be understood by those skilled in the art that conventional imaging processing systems usually provide processor consistency wherein instructions are executed in the order that they are requested from memory. It will also be understood that single-instruction multiple-data image processor 300 of the present invention is provided with weak processor consistency because block transfer controller 368, functioning as a separate instruction engine, can cause certain memory read requests to pass other memory requests.

As also previously described, access to global memory 366 is shared by all execution datapaths 358a-n within single-instruction multiple-data image processor 300. However, global memory 366 is not directly accessed by execution units 360a-n. Rather, execution units 360a-n access global memory 366 by way of memory interface 370 and global port 376 under the control of block transfer controller 368 and control line 378. Thus a selected port 363a-n may be coupled to global memory 366 by way of port 376. Furthermore, external global memory 366 may be global only in a conceptual sense within image processor 300. All that is required is that any execution datapath 358a-n can read or write any location in external global memory 366 by way of its external global memory port 363 and that external global memory 366 be external to execution datapaths 360a-n.

Within single-instruction multiple-data architecture 300 there is provided an improved method to more efficiently read blocks of data from system memory 364 and global memory 366 into local memories 362a-n by way of global memory port 363a-n, operate on the data within local memories 362a-n by way of lines 340, 332, 344, and write the results back to global memory 366, again by way of global memory port 363. In order to accomplish these more efficient block read and block write operations, single-instruction multiple-data image processor 300 is provided with block transfer instructions and block transfer architecture. The instructions and architecture are adapted to optimize the movement of data between local execution units 360a-n, local memories 362a-n and global memory 366. These input/output operations within single-instruction multiple-data image processor 300 are handled by autonomous synchronous block transfer controller 368.

Block transfer controller 368 within single-instruction multiple-data image processor 300 allows the transfer of two-dimensional arrays which are conformally displaced. This allows a subblock of a larger image to be copied in a single block operation for example. In general, using source and destination bit maps, conformally displaced blocks may be transferred even though they do not have the same aspect ratio or alignment in physical memory.

The specification for a block transfer operation initiated by a program within image processor 300 is actually a set of lists of individual block transfers. Each enabled execution datapath 358a-n builds a list of block transfer commands in its local memory 362a-n. A single block transfer initiate instruction eventually leads to the processing of all block transfer commands from the lists of every enabled execution datapath 358a-n. In addition, up to two sets of transfer lists can be pending at any time.

Referring now to FIG. 5, there is shown processing/memory time line 500. As illustrated by processing/memory time line 500, all block transfer operations within single-instruction multiple-data architecture 300 are split-phase transactions that occur concurrently with program execution. That is, a first program may perform a transfer during memory read block time segment 504 and perform processing during processing time segment 502. Overlapping with processing time segment 502, a second program may perform a transfer during memory read block time segment 506.

Referring now to FIG. 6, there is shown a schematic representation of the parameters that specify a memory-to-memory block transfer between global memory 366 and local memories 362a-n. It will be understood by those skilled in the art that while the schematic representation herein sets forth a transfer between global memory 366 and local memories 362a-n, the following discussion applies equally to transfers between system memory 364 and local memories 362a-n. This transfer takes place under the control of block transfer controller 368 within single-instruction multiple-data architecture image processor 300 of the present invention. It is possible to specify, for a single transaction, two-dimensional blocks 602a,b that are part of larger two-dimensional frame arrays 600a,b. Two dimensional frame arrays 600a,b may, respectively, reside within global memory 366 and within a selected local memory 362a-n.

Source frame 600a and source block 602a need not have the same aspect ratio as destination frame 600b and destination block 602b during memory-to-memory block transfers within image processor 300. However, the total number of elements and the width of source block 602a must be equal to the total number of elements and the width of destination block 602b.

In the block transfer request of image processor architecture 300 a set of block transfers is described by encoding the block transfer parameters in local memory 362a-n of each enabled execution datapath 58a-n. The block transfer is started by applying an initiate instruction to block transfer controller 368 by execution datapaths 360a-n by way of transfer control bus 344. It will be understood by those skilled in the art that this applying of the initiate instruction to block transfer controller 368 by way of transfer control bus 344 comprises posting of the transfer.

Referring now to FIG. 7, there is shown block transfer linked request list 700 containing a plurality of block transfer command templates 704, 706, 708 for initiating and specifying block transfers within single-instruction multiple-data image processor 300 of the present invention. Short block transfer command template 708 is an abbreviated form of long block transfer command templates 704, 706. Block transfer controller 368 uses default values for the pitch and width of specified memory blocks in order to permit the use of short command template 708 which specifies less transfer information than long command template 706. After posting a memory transfer, block transfer controller 368 fetches a command template such as long command template 704 or short command template 708 in order to perform the requested transfer.

If fetched command template 704 is part of a linked list containing further long command template 706 linked to fetched template 704, further template 706 is read after completion of the transfer performed under the direction of fetched template 704. Block transfer controller 368 then performs a further transfer according to further command template 706. Likewise, after the transfer specified by further command template 706 is completed, short command template 708 is fetched because short command template 708 is linked to command template 706.

Execution datapaths 358a-n maintain a status flag for each initiated block transfer operation in order to perform the completion check required for transfers under the control of block transfer controller 368. Each execution datapath 358a-n of image processor 300 may then check for the transfer to be completed by examining the associated status flag maintained by execution datapath 358.

Linked request list 700 within local memory 362a-n of single-instruction multiple data architecture 300 is thus a linked list of block transfer command templates 704, 706, 708. Each command template 704, 706, 708 in linked request list 700 specifies the parameters for a programmed block transfer of data between local memory 362a-n and system memory 364 or global memory 366 of image processor 300. These parameters may be specified explicitly, implicitly or may be determined by default.

For example, internal address field 720 of linked request list 700 may specify a starting address 604 of two-dimensional block 602b within two-dimensional frame array 600b. Two-dimensional frame array 600b resides in the same local memory 362a-n as linked request list 700. External address field 722 of long command templates 704, 706, 708 specifies a destination starting external address 606. External address 606 is the starting address of two-dimensional block 602a within two-dimensional frame array 600a.

Long command templates 704, 706 also contain pitch information for permitting block transfer controller 368 to perform memory-to-memory transfers within single-instruction multiple-data image processor 300. External pitch field 724 of long command templates 704, 706 specifies the external pitch of two-dimensional frame array 600a. Internal pitch field 728 of long command templates 704, 706 specifies the internal pitch of two-dimensional frame array 600b. Short command template 708 is not provided with external pitch field 724 or internal pitch field 728. The width of both two-dimensional blocks 602a,b is stored in pitch field 728.

Link address field 730 of long command template 720 points to long command template 706. The link address field 730 of long command template 706 in turn points to short command template 708. Note that, in addition to external pitch field 704 and internal pitch field 728, width field 726 of long command templates 704, 706 is not present in short command template 708.

Thus, linked request list 700 within image processor 300 is a specification for a series of individual block transfers by block transfer controller 368. Linked request list 700 of each datapath 358a-n is constructed by its respective execution unit 360a-n in its respective local memory 362a-n. The links in linked request list 700 point to the next template 704, 706, 708 in list 700. Templates 704, 706, and 708 are all resident within local memory 362a-n of the same execution datapath 358a-n. A transfer list 700 may be terminated by setting the address in link field 730 of the last valid command template to some suitable end-of-list indication.

Each enabled execution datapath 358a-n of architecture 300 supplies its linked request list 700 to block transfer controller 368 for a transaction. There may be up to two block transfer request lists 700 simultaneously initiated by each execution datapath 358a-n. In general the number of linked request lists 700 in a transaction controlled by block transfer controller 368 may be up to two times the number of enabled execution datapaths 358a-n.

Memory address 702 of first command template 704 in linked transfer list 700 within local memory 358a-n is always located at the root pointer register of an associated execution unit 360a-n. A microinstruction that posts a block transfer identifies either first linked list 702 or second linked list 710 as corresponding to the root pointer for the transfer. Each enabled execution datapath 358a-n of image processor 300 has its own valid transfer list 700 in place when a transfer is posted.

All of the block transfers for an initiate instruction under the control of block transfer controller 368 within image processor 300 must be completed before any transfer is processed for any later initiate instruction. This first-in, first-out ordering is essential to maintain the sequential semantics of the single instruction stream of single-instruction multiple-data image processor 300 of the present invention. Thus, if one initiate posts a write to system memory 364 or global memory 366 and the next initiate posts a read of system memory 364 or global memory 366, it is guaranteed that, regardless of the order in which each of the individual datapaths 358a-n are seized, all writes are finished before any read begins. This rule requires only that sets of transfers be initiated and completed in order. This rule does not preclude buffering multiple requests.

As previously described, each local memory 362a-n within single-instruction multiple-data image processor 300 is provided with dual port architecture. One port of the dual port architectural is global memory port 363a-n or external memory port 363a-n. Global memory port 363a-n of each local memory 362a-n is dedicated to data transfers between local memory 362a-n and system memory 364 or global memory 366. Global memory ports 363a-n are formed by transfer control lines 340, 342, and 344.

The other port of the dual port architecture of each local memory 362a-n of image processor 300 is local memory port 361a-n. Local memory port 361a-n is dedicated to transfers between local memories 362a-n and execution units 360a-n. Local memory port 361a-n of the dual port architecture of system 300 is formed of two separate ports, an A port and a B port. Transmission of data by way of the program port of local memory ports 361a-n is under the control of the instructions issued by sequence controller 352 having instruction memory 380. As a result, single-instruction multiple-data architecture 300 can support access to global memory 366, including block transfers, while simultaneously continuing execution within execution units 360a-n.

For example, memory read block time segment 506 of processing/memory time line 500 is simultaneous with processing time segment 502 for its entire duration. This is accomplished by converting the read and write operations of single-instruction multiple-data image processor 300 into split phase transactions comprising an initiate operation and a transfer complete synchronization. This capability is essential for sustaining the high external global memory bandwidth required by video signal processing applications.

Thus an initiate instruction only initiates the block transfer operation while sequence controller 352 continues to issue instructions to execution units 360a-n while the transfer takes place. It will be understood by those skilled in the art that a program executing within execution units 360a-n of image processor 300 must resynchronize with global memory 366 or external memory 366 after completion of the transfer by block transfer controller 368.

In order to simplify the following example, the instruction sequence of Table IX is written for image processor 300 having a single execution datapath 358a.

                  TABLE IX                                                         ______________________________________                                         /* wait for the first block to be read into temp.sub.-- block1 */              start.sub.-- read block(original.sub.-- image[0],temp.sub.-- block1);          io.sub.-- wait();                                                              /* initiate read of next block into temp.sub.-- block2 */                      start.sub.-- read.sub.-- block(original.sub.-- image[1],temp.sub.--            block2);                                                                       for (k = 0; k < NUMBEROFBLOCKS; k = k + 2);                                      /* transform two blocks per iteration */                                       DCT.sub.-- block(temp.sub.-- block1);                                          io.sub.-- wait();                                                              start.sub.-- write.sub.-- block(xform.sub.-- image[k],temp.sub.--            block1);                                                                         start.sub.-- read.sub.-- block(original.sub.-- image[k+2],temp.sub.--        block1);                                                                         DCT.sub.-- block(temp.sub.-- block2);                                          io.sub.-- wait();                                                              start.sub.-- write.sub.-- block(xform.sub.-- image[k+1],temp.sub.--          block2);                                                                         start.sub.-- read.sub.-- block(original.sub.-- image[k+3],temp.sub.--        block2);                                                                       };                                                                             ______________________________________                                    

The instruction sequence of Table IX uses a straight-forward double buffering technique. In this double buffering technique, while temp₋₋ block1 within local memory 362a is transformed, temp₋₋ block2 within local memory 362a is loaded with the next block from global memory 366. After the transform of the first block is completed, a write of the transformed data of block1 from local memory 362a to global memory 366 is initiated. This is followed by a read of the next data from global memory 366 for block1. Execution of the instruction sequence of Table IX then advances to transforming temp₋₋ block2 simultaneously with writing the results of temp₋₋ block1 back to global memory 366. The new read of temp₋₋ block2 from global memory 366 proceeds in parallel with this write of temp₋₋ block1.

The io₋₋ wait() of Table IX causes sequence controller 352 to wait until all input/output transfers have been completed within execution datapaths 358a-n before proceeding. This guarantees that a previously initiated read or write by execution unit 360a-n is no longer using the source block and that the contents of the destination block are valid. In general, the io₋₋ wait() is implemented in image processor 300 with a conditional branch instruction which tests the block transfer done flag local to each execution datapath 358a-n.

As previously described, processing/memory time line 500 is a representation of the processing and memory accesses of the multibuffered input/output of single-instruction multiple-data image processor 300. The latency of input/output transfers are hidden by the overlapped computation on the blocks. For example, consider the blockwise discrete cosine transform of an image within the architecture of single-instruction multiple-data image processor 300. The basic discrete cosine transform algorithm has considerable parallelism. The image to be transformed is tiled by a set of uniformly sized blocks and the discrete cosine transform is independently computed over each of the blocks. Because there are no data dependencies among the individual block transforms, all sets of block transforms may be computed in parallel by parallel execution datapaths 358a-n.

Referring now to FIG. 8, there is shown single-instruction multiple-data image processor 800 having four execution datapaths 806a-d. Single-instruction multiple data image processor 800 is an alternate embodiment of image processor 300. Sequence controller 802 of image processor 800 applies instructions from instruction memory 801 to execution units 814a-d of execution datapaths 806a-d by way of instruction broadcast line 804. When performing block transfer and block transform operations, single-instruction multiple-data architecture 800 has the simplification of a single instruction stream as previously described with respect to single-instruction multiple-data image processor 300.

The instruction sequence of Table X may be provided within instruction memory 801 to program image processor 800 to perform a blockwise discrete cosine transform of original image memory block 818 stored in global memory 816 to provide a transform image stored in transformed memory image block 820. As also previously described, the instruction sequence of Table X is executed simultaneously by all execution datapaths 806a-d of four execution datapath image processor 800.

The instruction sequence of Table X may perform the discrete cosine transform required within the instruction sequence of Table IX. The discrete cosine transform instruction sequence of Table X is sequential except that the outer loop j is executed only one-fourth as many times as the inner loop k. This is due to the four-fold parallelism of execution datapaths 806a-d. The loop induction variable, j, of the outer loop takes the values 0,4,8 . . . .

                  TABLE X                                                          ______________________________________                                         DCT.sub.-- Image;                                                                global int original.sub.-- image[ ], xform image [ ];                          local int j, k, temp.sub.-- block[BLOCKSIZE];                                  for (j = 0; j <NUMBEROFBLOCKS;j = j + 4) {                                        k = j + THIS.sub.-- DP.sub.-- NUMBER;                                       read.sub.-- block(original.sub.-- image[k], temp.sub.-- block);                DCT.sub.-- block(temp.sub.-- block);                                           write.sub.-- block(xform.sub.-- image[k], temp.sub.-- block);                  };                                                                           ______________________________________                                    

The value of the constant THIS₋₋ DP₋₋ NUMBER, which is used to determine the loop induction variable k, depends upon which execution datapath 806a-d is performing the operation. This permits each execution datapath 806a-d of image processor 800 to select a different block number, k, to process by adding the execution datapath-dependent value THIS₋₋ DP₋₋ NUMBER to the value of j. Thus the constant THIS₋₋ DP₋₋ NUMBER, which is unique to each execution datapath 806a-d, is equal to zero for execution datapath 8061a, one for execution datapath 806b, etc. Execution datapath 806a therefore processes block numbers k=0,4,8. . . of original memory image block 818 from global memory 816, while execution datapath 806b processes blocks k=1,5,9. . . etc.

All execution datapaths 806a-d copy their assigned blocks k into their respective temp₋₋ block 812a-d, a temporary array in local memory 810a-d of each execution datapath 806a-d. The assigned blocks of original image memory block 818 copied from global memory 816 into respective local memories 810a-d are then transformed by the respective execution units 814a-d of execution datapaths 806a-d. The resulting transformed blocks within each execution datapath 806a-d are then copied back to transformed memory image block 820 within global memory 816. While original image block 818 and transformed image block 820 are in shared global memory 816, the four sets of values of the loop induction variables i and k reside in respective memory locations 822a-d. Memory locations 822a-d for storing the local values of i and k are provided in each local memory 810a-d of each execution datapath 806a-d, along with the local values of temp₋₋ block 812a-d.

In addition to the simplicity of a single instruction stream like that of conventional sequential processors (not shown), single-instruction multiple-data image processor 800 provides significant efficiency advantages for those algorithms that may be optimized for single-instruction multiple-data systems. In addition to the economics of sharing single sequence controller 802 and associated instruction memory 801, an important advantage is the synchronization of multiple execution datapaths 806a-d. For example, during the blockwise discrete cosine transform of the instruction sequence of Table X, it is easy to determine when all execution datapaths 806a-d have completed a current set of block transforms. The block transforms are completed when the last instruction in the block transform code has executed.

A very important feature of single-instruction multiple-data image processor 300 is block transfer controller 368. Block transfer controller 368 performs conflict resolution and controls the flow of data within image processor 300. The transfers are divided into three groups according to their bandwidth requirements. These three groups of transfers are designated Group I, II and III within the method and system of the present invention, Group I transfers are those transfers within image processor 300 having relatively low bandwidth requirements. Group II transfers are those transfers which are bursty in nature and are not initiated from within single-instruction multiple-data image processor 300. Group III transfers are those having high bandwidth requirements that are of lower priority than the transfers of Groups I and II. For example, Group II transfers may be initiated by an external direct memory access device such as two-dimensional direct memory access transfer.

The transfers within Groups I, II, III may be assigned relative local priorities. For example, video random access memory transfers within Group I may have a higher local priority than audio transfers which, in turn, have a higher local priority than refresh cycles for local memories 362a-n. Local arbitration of these relative local priorities within Group I permits relatively high priority low bandwidth transfers by block transfer controller 368 to take precedence over relatively low priority low bandwidth transfers. With respect to relative local priorities within Group II, system scalar read/writes may have a higher local priority than system burst read/writes, which in turn may have a higher priority than two-dimensional direct memory access transfers. Within Group III, cache line misses may have a higher local priority than scaler transfers which, in turn, may have a higher local priority than block transfers. With respect to block transfers, Block transfer controller 368 prioritizes block transfers of data from global memory 366 to local memories 362a-n when requested by execution units 360a-n. Block transfer controller 368 also generates addresses and controls for transfers from local memories 362a-n to global memory 366 or system memory 364. Groups I, II and II are serviced by block transfer controller 368 within image processor 300 in the following manner:

Group I--Group II--Group I--Group III

Group I--Group II--Group I--Group III

[Repeat]

This reiterating method of poling is used in order to prevent high-priority, high-frequency requests for service by block transfer controller 368 from locking out requests which occur less often and are less critical. This is necessary because the less critical requests must still be performed in order for single-instruction multiple-data processor 300 to operate properly.

One request in each Group I, II, III is serviced during each iteration of the priority scheme. For example, when Group I is poled the pending request having the highest priority within Group I is serviced by block transfer controller 368. Any further requests from Group I must wait for the next iteration. Next, Group II is poled by controller 368 and the highest request within Group II is serviced. Within Group II, the number of transfers permitted for servicing by controller 368 may be limited, for example, to sixteen transfers. Additionally, if the servicing of a request in Group II requires a smaller bandwidth than sixteen transfers, the bus may be immediately released to the next transfer group. These features allow block transfer controller 368 to transfer data more efficiently and also help prevent lower priority requests from being locked out.

Following the poling of Group II, Group I is polled again, and the highest local priority request pending within Group I is serviced by block transfer controller 368. Following this second polling and servicing of Group I, Group III is again polled and the highest local priority request pending in Group III is serviced by controller 368. The number of transfers permitted during the servicing of a Group III polling may also be limited, for example, to sixteen transfers.

With respect to Group I transfers the typical bandwidth requirements may be as follows. Virtual random access memory transfers may have a bandwidth of approximately sixty four kilohertz based upon a one kilobyte by one kilobyte type resolution display. The second level of local priority within Group I, audio transfers may be on the order of four kilohertz based upon conventional thirty two kilobits per second audio rate applications. The third level of local priority within Group I, refresh cycles, may have a rate of sixty four kilohertz. The bandwidth for the refresh cycles may be sixty four kilohertz for a nominal refresh rate of two hundred fifty six cycles every four milliseconds. There may be no arbitration within the three types of transfers in Group I if all three are of low enough bandwidth and high enough priority that the requests may be serviced in time without arbitration.

With respect to Group II local arbitration, it is difficult to characterize the bandwidth requirements of the transfers within this group because of their bursty nature. These transfers are highly dependent on system configuration. Basically, the nature of these transfers is bursty and regulated in part by the traffic conditions on the system bus interface.

Additionally, it is permitted to impose no relative local priority within Group III if all three types of request are equally likely and equally important. In this alternate embodiment of method x the transfers of Group III are processed on a first come, first served basis. There is by definition arbitration between transfers involving the system bus because system 300 contains two hi-directional burst buffers which allow up to sixteen word transfers to be captured. It also contains a set of dual scaler buffers, which are used to capture scaler accesses. These buffers allow scaler and burst request to be performed even if the bus resource is unavailable.

With respect to Group III local arbitration, the band width requirements are highly dependent upon system configuration.

The functions performed by block transfer controller 368 during block data transfers of data between global memory 366 and local memories 362a-n include arbitration of transfer requests of competing global memory 366 and execution units 360a-n, address generation and control for two-dimensional block transfers between global memory 366 and local memories 362a-n, control for scalar, first-in first-out, and statistical decoder transfers between local memories 362a-n and global memory 366 and address generation and control for block instruction load following cache miss.

A number of different types of transfers requiring input/output access arbitration by block transfer controller 368 may take place between global memory 366 and local memories 362a-n. These include fetching instructions from global memory 366. Image processor system 300 initializes the process by downloading instructions from system memory 364 to global memory 366. On power up of image processor 300 the instructions are loaded from system memory 364 or global memory 366 into the controller.

Different types of transfers may be prioritized by block transfer controller 368 as follows, proceeding from highest priority to lowest priority: (1) instruction, (2) scalar, first-in, first-out and statistical decoder, and (3) block transfer. Thus block transfer controller 368 not only prioritizes and arbitrates within image processor 300 based upon whether a request is an instruction type of request or a data type of request. Block transfer controller 368 also prioritizes and arbitrates based upon the subtypes of data.

In order to handle higher priority transfers while suspending lower priority transfers within Group III, the transfer having higher priority is allowed to gain access to transfer data bus 340 of global memory ports 363a-n at the next available memory cycle boundary. After the completion of the higher priority transfer within Group III, the suspended lower priority transfer is resumed. Thus it will be understood that single-instruction multiple-data image processor 300 of the present invention is provided with weak processor consistency. In the weak processor consistency of image processor 300 input/output operations are not necessarily executed in the order in which they are applied to execution units 360a-n.

Block transfer controller 368 supports multiple levels of suspension within Group III. For example, a block transfer within image processor 300 may be interrupted by a scalar access, which may be interrupted by an instruction load. In this case, block transfer controller 368 suspends the block transfer at the next available memory cycle boundary and starts performing the scalar access. When the cache miss occurs, the scalar access is interrupted at the next memory cycle boundary and the block of instructions is fetched. After the instruction fetch is complete,, block transfer controller 368 resumes the scaler access starting with the last execution unit 360a-n serviced. Upon completion of servicing of all the scaler accesses posted, the block transfer is resumed.

When execution units 360a-n require data, they assert a request flag on line 340 to block transfer controller 368. Block transfer controller 368 then arbitrates the requests from the competing execution units 360a-n, and grants an execution unit 360a-n access to the bus. The execution unit 360a-n which was granted access by block transfer controller 368 retains control of the bus until completion of the transaction unless a request of higher priority is posted by a different execution unit 360a-n.

Block transfer controller 368 services all requests posted at the same time by an execution unit 360a-n before starting the request of another execution unit 360a-n, In order to ensure that no execution unit 360a-n is locked out by posting of an intervening transfer, block transfer controller 368 uses a serial polling scheme to service requests from the competing execution units 360a-n. In this serial polling scheme the last execution unit 360a-n serviced by block transfer controller 368 is not eligible for servicing by controller 368 again until outstanding requests of all other execution unit 360a-n have been serviced,

The two-dimensional block transfer method within single-instruction multiple-data image processor 300 is a direct memory access mechanism for moving one or several rectangular images of arbitrary size between global memory 366 and local memories 362a-n. The operation of the two-dimension block transfer by block transfer controller 368 is autonomous with respect to program execution by execution units 360a-n of single-instruction multiple-data image processor 300, Synchronization between the program being executed by execution units 360a-n and the block transfer operation controlled by block transfer controller 368 is accomplished by two interactions: the transfer request and the completion check. The time duration of these transfers by block transfer controller 368 within single-instruction multiple-data processor 300 may be mathematically characterized in order to analyze the priority scheme of the present invention. For example, within Group I the duration of virtual random access memory transfers, VramXfer, the duration of the audio transfers, AudioXfer, and the duration of the refresh cycles, Refresh, may be Characterized in a conventional manner.

For example, it will be understood that random access memory transfers are essentially a one transfer cycle to external memory. The time required for this transaction, from the receipt of the transfer code by transfer controller 368 until the virtual random access memory transfer is completed., is:

    VramXfer=Tovr+Tmem

where Tovr is the virtual random access memory transfer overhead of five cycles. Tmem is the memory access time of the virtual random access memory, as programmed in the local bus interface. This access time may typically be eight cycles.

With respect to audio transfers within Group I, these transfers are essentially one transfer cycle to system memory 364 or global memory 366. The time required for this transaction, from the receipt of the transfer code by block transfer controller 368 until the actual transfer is completed, is:

    AudioXfer=Tovr+Tmem

where Tovr is the virtual random access memory transfer overhead of five cycles as previously described and Tmem is the memory access time of the virtual random access memory, as programmed in the local bus interface. This virtual memory access time may typically be eight cycles as previously described.

With respect to the duration of refresh cycles within Group I of single-instruction multiple-data processor 300, two refresh cycles are performed at the programmed refresh interval. Depending on the number of banks of dynamic or virtual random access memory, as programmed in the memory configuration registers, image processor 300 may perform a pair of transfer cycles to each bank, for up to two banks. The time required to complete this transfer is given by the following formula: ##EQU2## where Tovr may typically be five cycles and Tmem, the memory access time of the VRAM, may typically be eight cycles. Bank is the number of dynamic random access memory banks requiring refresh. This number may typically be one or two.

With respect to Group II transfers within image processor 300, a complicating factor in the determining the performance of transactions using the system bus interface is the transversing of the different clock regimes. All transactions to and from system interface bus 365 must be resynchronized when these regimes are crossed. This penalty must be taken into account in calculating the transfer duration.

The scalar write operation of Group II includes another bus master arbitrating for the system bus, and writing a single thirty two bit word into a local memory 362a-n of a selected datapath 360a-n. The total time for this transaction is:

    Scalarwrite=Tarb+Tovr+Tmem

where Tarb is the arbitration and other overhead in the other master negotiating for the system interface bus, Tovr is the scalar write transfer overhead, having a value of six cycles, and Tmem is the memory access time of the dynamic or virtual random access memory, as programmed in the local bus interface. This access time may typically be eight cycles for a scalar write within image processor 300 of the present invention.

The scalar read operation of Group II involves another bus master arbitrating for the system bus, and reading a single thirty two bit word into local memories 362a-n of image processor 300. The total time for this transaction is:

    ScalarRead=Tarb+Tovr+Tmem

where Tovr is the scalar read transfer overhead, having a value of twelve cycles, and Tmem is the memory access time of the dynamic or virtual random access memory as previously described. This access time may typically be eight cycles.

The burst write operation of Group II involves another bus master arbitrating for the system bus, and writing a burst of up to sixteen thirty two bit words into local memories 362a-n of image processor 300. The total time for this burst write transaction is: ##EQU3## where Tarb is the arbitration and other overhead in the other bus master negotiating for the system interface bus, Tovr is the scalar write transfer overhead of six cycles, Tmset is the RAS precharge time for the first access in the burst to a dynamic or virtual random access memory, as programmed in the local bus interface. This access time may be typically five cycles. Tpage is the page access time of the local memory dynamic or virtual random access memory, as programmed in the local bus interface configuration registers. This access time may typically be three cycles. The summation index, words, is the number of thirty-two bit words in the transaction.

Also within Group II the burst read operation involves another bus master arbitrating for the system bus, and writing a burst of up to sixteen thirty two bit words into local memories 362a-n. The total time for this transaction is: ##EQU4## where Tovr is the burst read transfer overhead of twelve cycles.

Also within Group II the two-dimensional direct memory access operation involves another bus master arbitrating for the system bus, and writing a burst of up to sixteen thirty two bit words into local memories 362a-n. The total time for this transaction is: ##EQU5## where Tovr is the scalar read transfer overhead of twelve cycles, where Tpage is the page access time of the local memory dynamic or vertical random access memory, as programmed in the local bus interface configuration registers. This access time may be three cycles, and words, the summation index, is the number of thirty two bit words in the transaction.

With respect to Group III transfers by block transfer controller 368 within single instruction multiple-data processor 300, scalar transfers include both scalar writes and scalar reads. The total time required for these transfers, from the posting of a scalar transfer by writing to the scalar transfer register until the data is in external memory 364, is: ##EQU6## where EM_(i) is the execution mask for execution unit 360a-n involved in the arbitrated scalar transform. A mask value EM_(l) of zero means that involved execution unit 360i of execution units 360a-n is active and a mask value of EM_(i) one indicates that involved execution 360i of execution units 360a-n is not active. Tovr is the overhead for servicing each execution unit 360a-n. This overhead is typically fifteen cycles.

Tmem_(i) is the total number of memory cycles required to service the scalar for execution unit 360i. Pagemiss is a boolean indicator wherein a value of one indicates that the address for the memory cycle is not in the same page in the external memory as the previous access and a value of zero indicates that the access is on the same page and that no further address setup is thus required. Tad is the memory setup time for typical dynamic memories, typically five cycles for read and write operations, and Tpage is the page mode cycle time which is typically three cycles for a read or write operation. Using the typical values for the expressions of the time duration of a transfer request, block transfer controller 368 of single-instruction multiple-data processor 300 may provide four scalar write cycles to four different memory pages every forty seven cycles. This translates into a scalar write every eleven cycles or a byte every three cycles.

Further to the scalar transfer within Group III, the total time required from the posting of a scalar transfer, from writing to the scalar transfer register until the data is read from external memory 364, is: ##EQU7## where Tovr is the overhead for servicing each execution unit 362a-n, typically twenty-one cycles, and the Tad memory setup time is again five cycles. Using the typical numbers for a transfer request, single-instruction multiple-data image processor 300 may provide four scalar read cycles to four different memory pages every fifty three cycles. This translates into a scalar write every twelve cycles or a byte every three cycles.

Scalar read broadcasts within image processor 300 are a special case of the above formulas. During scalar read broadcasts only one execution unit 362a-n is active, and Tmem_(i) is zero since no external memory cycles are generated.

If a block transfer has been initiated while a instruction load (cache miss), or scalar transfer, or FIFO access is being serviced, it must wait until the higher priority request has been finished. If it is not interrrupted by a higher priority transfer, it executes the block transfer for each template specified in a linked list, for each execution unit that was active at the time the block transfer posting occurred. Servicing of the block posting starts at execution unit 358a and continues to execution unit 358n, skipping over execution units 358a-n that are not active during the instruction cycle that the block transfer is posted.

The actual transfer process may be divided into several operations. First, the internal transfer bus must be arbitrated, and permission given for an execution unit 360a-n to transfer data over that bus. It takes several cycles over to initiate the transfer, fetch the root pointer, and indicate the end of the transfer. This overhead is required for each active execution unit 360a-n posting a block transfer. It is not required for subsequent transfers in a linked list for the same execution unit 360a-n, that are part of the same posting. The next task is fetching the template, which is variable length, as specified in the command word of the template. The final task is executing the transfer operation.

The performance of the block transfer is bounded by the memory access rate. Additionally it is dependent on the efficiency of the arbitration protocol for the memory resource. In a typical system implementation, single-instruction multiple-data image processor 300 has relatively unrestricted access to the local memory bus. The availability of the system bus depends upon bus protocol. Image processor 300 may be a bus master, and as such, it may throttle other devices that are saturating the bus. As a bus master, image processor 309 can guarantee one sixteen bit word burst every seventeen cycles where a word is understood to be formed of thirty-two bits. Thus there is a dependence on the local memory access time. Because it can only receive data at a certain rate it may be held up. Assuming a zero wait state to external memory the number of cycles required to complete all block transfer for a single posting is: ##EQU8## where Tstartovr is the start-up overhead for the initial transfer.

Typically for this block transfer four cycles are required for overhead from the time the ibtN instruction is executed until the time a request is granted. Tstopovr is the two cycles required to stop each block transfer in the linked list, after the last data transaction has taken place. Template_(i) is the number of templates in the linked list for execution unit 362i and Tempfetch_(in) is the number of cycles required to fetch the n^(th) template of execution unit 362i. Typically between eight and ten cycles are required are required to fetch the template. Five cycles are required to grant access to the program port of a particular data memory, fetch the root pointer, five cycles are required to read a long template, and three cycles are required to read a short template. Tmem_(in) is the total number of memory cycles required to service the block transfer, as specified by the n^(th) template of execution unit 362i. This includes the overhead associated with a page miss. Size_(in) is the size of the transfer block in bytes, as specified by the n.sup. th template of the execution unit 362i, and Buswidth is the width of the resource bus. This width may be four bytes for system bus and four or eight bytes for local bus. ##EQU9## Integer (expression), Width_(in) is the width of the transfer block in bytes, as specified by the n^(th) template of execution unit 362h, Pagesize is the size of a physical page of memory, in bytes, as determined by the page size register in the bus interface unit, Pitch_(in) is the external pitch of the transfer block in bytes, as specified by the n^(th) template of execution unit 362i, Tpgmiss_(in) represents page miss overhead. Calculates the number of page boundaries that are crossed during a block transfer for execution unit 362i, during the servicing of template n. Block read broadcasts are a special case of the above formulas, wherein only one execution unit 360a-n is active.

With respect to the instruction read within Group III, once an instruction cache miss has occurred it must wait until the current memory cycle is over before being serviced. In the worst case it must wait the complete memory cycle time. Once clear, it takes five cycles to arbitrate and get the miss address from instruction controller 352. After receiving this information, an entire block of eight sixty-four bit instructions, broken up into sixteen words of thirty-two bits each, are loaded into instruction sequencer 352. Instruction sequencer 352 then reassembles the data back into an instruction to be applied to datapaths 358a-n by way of instruction broadcast line 356. The total time required for this access is: ##EQU10## where Toverhead is the start-up overhead for each execution unit 362a-n. A total of six cycles is needed for this transaction. These six cycles include five cycles for the overhead required to initiate the transfer and one cycle to finish the transfer. Instr is the number of instructions loaded into instruction sequencer 352 by way of block transfer controller 358. This has a value of eight. Instrlength is the length of each fetched instruction. Within image processor 300 this instruction length may be sixty four bits. Buswidth, the width of the resource bus, may be one, two, or four bytes for system bus and four or eight bytes for local bus. Tmem is the total number of memory cycles required to service the instruction cache load a value of one for. Pagemiss indicates that the address for this memory cycle is not in the same page in the external memory as the previous access. A value of zero for page indicates that the access uses the same page and no additional address setup is required. Since the instructions are fetched sequentially over a five hundred twelve byte range, there may be at most one Pagemiss during the entire instruction fetch operation. Tad, the memory setup time for typical dynamic memories, is again assumed to be five cycles for reach operations and Tpage, the Page mode cycle time is assumed to be three cycles for a page hit.

As previously described, single-instruction multiple-data image processor 300 is provided with a linked list structure 700 to specify block transfer operations to block transfer controller 368. Each such block transfer linked request list structure 700 for specifying transfers to controller 368 within image processor 300 is provided with a root pointer and one or more block transform command templates 704, 706, 708. Two linked request lists 700 are supported for each execution unit 360a-n, each request list 700 of an execution unit 360a-n having its own set of one or more command templates 704, 706, 708. The programmer of image processor 300 constructs and stores linked request lists 700 in local memories 362a-n prior to initiating a transfer under the control of block transfer controller 368. When a block transfer is initiated by an active execution unit 360a-n, only active execution units 360a-n within image processor 368 are serviced.

In order to provide linked request list 700 within local memories 362a-n, a user of single-instruction multiple-data image processor 300 writes to root pointer registers (not shown) within execution datapaths 358a-n. Additionally, the user writes command templates 704, 706, 708 into local memories 362a-n to set up the required block transfer by block transfer controller 368. The root pointer register holds the starting address of first command template 704 in each execution unit 360a-n.

Command template 704, which contains the description of the first two-dimensional transfer, varies from one execution datapath 362a-n to another within image processor 300. Because multiple command templates 704, 706, 708 may be connected in linked request list 700, as previously described, and two linked lists 700 may be supported, the transfer of multiple independent blocks of data between global memory 366 and local memories 362a-n within datapaths 358a-n of image processor 300 under the control of block transfer controller 368 may thus be initiated by a single instruction.

As previously described, there are two types of command templates, long command templates 704, 706 and short command template 708. The information within short command template 708 is a subset of the information within long command template 704. Within block transfer controller 368 there are three default registers: the default external pitch register, the default internal pitch register and the default width register. When using long command template 704, or long command template 706, block transfer controller 368 uses the pitch and width value specified fields 724, 726 of long command templates 704, 706. When using short command template 708, block transfer controller 368 uses the pitch and width values specified in default registers. The default register contents may be modified by the user of single-instruction multiple-data image processor 300. When the user performs this modification of the default registers, the default register contents may be updated to contain new external pitch parameters, internal pitch parameters and width parameters as specified by the user.

Prior to initiating a block transfer by block transfer controller 368, the user of single-instruction multiple-data image processor 300 must check a block transfer done bit to determine that the previous block transfer is completed. Initiation of a block transfer without checking the previous transfer block done bit may cause indeterminate results as previously described. After the previous block transfer is completed and the done bit is set, the user may set a block transfer request bit in block transfer controller 368. This is done by a block transfer initiation instruction. The done bit is cleared as soon as the block transfer is initiated. Several active execution units 360a-n may request block transfers and block transfer controller 368 may arbitrate among active execution units 360a-n to start the block transfers.

After a block transfer is initiated, block transfer controller 368 executes the block transfer sequences starting with execution unit 360a. Block transfer controller 368 fetches the root pointer address of first command template 704 from execution unit 360a if execution unit 360a is active. Block transfer controller 368 uses this root pointer address to load first command template 704 of linked request list 700 of execution unit 360a. After command template 704 is loaded, block transfer controller 368 transfers a memory block between local memory 362a and global memory 366 according to the specifications within command template 704.

When the first block transfer is completed, according to command template 704, block transfer controller 368 uses link address field 730 of command template 704 to fetch next command template 706 of linked request list 700 of execution unit 360a. Execution of the next block transfer according to command template 706 is then performed. Once block transfer controller 368 loads a link address field 728 having a null, the next active execution unit 360b-n is serviced by block transfer controller 368. The root pointer register of next active execution unit 360b-n is used to fetch the first link address.

When block transfer controller 368 completes linked request lists 700 of all active execution units 360a-n within single-instruction multiple-data image processor 300, a block transfer done condition bit is set. When one set of linked request lists 700 within local memories 362a-n of active datapaths 360a-n is completed in this manner, block transfer controller 368 is prepared to service another set of linked request lists 700 when initiated by execution units 360a-n.

Two block transfer done bits are therefore required in the condition code register (not shown) of each execution datapath 360a-n. One block transfer done bit is provide for each of the two possible linked request lists 700 which may be stored in its local memory 362a-n. These two block transfer done bits are determined by block transfer controller 368. After each transfer by block transfer controller 368 according to linked request lists 700 is finished, the corresponding block transfer done bit in the condition code register of the serviced datapath 360a-n is set by controller 368. The block transfer done bits are cleared by block transfer controller 368 when the following block transfer is initiated by execution units 360a-n. The block transfer done bits are microcode condition codes. The microcode can use a "branch if condition" instruction to generate an IO₋₋ WAIT() function when required for a block transfer between global memory 366 and local memories 362a-n within image processor 300.

Block transfer operations within single-instruction multiple-data image processor 300 have lower access priority than instruction fetches and scalar transfers as previously described. Block transfer controller 368 therefore suspends a lower priority block transfer operation requested by an execution unit 360a-n when a transfer operation of a higher priority is requested by a different execution unit 360a-n. Block transfer controller 368 and memory interface 370 first finish any outstanding read or write request for block transfers and save the parameters of the command template 704, 706, 708 specifying the block transfer in progress.

The parameters saved by block transfer controller 368 when a higher priority transfer is initiated include the next address in external global memory 366 and the next address in local memory 362a-n of the datapath 358a-n being serviced. These parameters are saved in registers (not shown) within block transfer controller 368. Block transfer controller 368 then services the higher priority access. When the higher priority access is complete, block transfer controller 368 retrieves the saved address parameters from its registers and resumes or reinstates the suspended block transfer.

As previously described, only the instruction fetch and the scalar transfer have higher priority than the block transfer within single-instruction multiple-data architecture 300 as controlled by block transfer controller 368. A block transfer in an interrupt routine does not have higher priority than an initiated block transfer. Thus initiated block transfer is serviced first by controller 368. Block transfer controller 368 thus provides interruptible memory transfers between local memories 362a-n and system memory 364 or global memory 366. If a block transfer is initiated within single instruction multiple-data image processor 300 while a cache miss, scalar transfer, or first-in first-out access is being serviced by controller 368, it must wait until the higher priority request is finished.

Referring now to FIG. 9, there is shown scalar access transfer system 1000 of single-instruction multiple-data image processor 300. Within scalar access system 1000, there are two sets of scalar transfer controls for block transfer control 368. Within each execution unit 360a-n of image processor 300, there are two scalar address registers 1001, 1002 and two scalar data registers 1004, 1006. Scalar data registers 1004, 1006 may be thirty two bits wide. Scalar address register 1001 and scalar data register 1004 within execution unit 360a-n are associated with the first set of transfer controls. Scalar address register 1002 and scalar data register 1006 are associated with the second set. Address registers 1001, 1002 hold the address in external memory 364, 366. Address registers 1001, 1002 may be loaded by either of two buses, the A-Bus or the B-Bus. Each scalar data register 1004, 1006 can be read or written by either the A-Bus or the B-Bus.

For an output scalar transfer, block transfer controller 368 fetches the contents of scalar address register 1001 or scalar address register 1002 as well as data register 1004 or data register 1006. This fetch is performed by way of transfer data bus 340. For an input scalar transfer, block transfer controller 368 fetches scalar address register 1001, 1002, loads to interface 370, and fetches the return data load to data register 1004, 1006 through transfer data bus 340. The scalar access may support byte, half word, and word alignment. Byte and half word data fetched and loaded in scalar data registers 1004, 1006 are right justified.

For a scalar write, scalar data register 1004 or scalar date register 1006 must be written first. The scalar output address register may then be written. Writing to the scalar output register initiates a scalar output transfer request to block transfer controller 368. For the scalar input transfer, the user of image processor 300 writes scalar input address register 1001 or scalar input address register 1002. The scalar done bit is cleared when the scalar transfer is posted. After the scalar transfer is initiated, block transfer controller 368 samples all active execution units 360a-n and processes the scalar transfers starting with execution unit 360a. An execution unit 360a-n is determined to be active when its execution mask flag is reset. The scalar done bit of an active execution unit 360a-n must be checked by block transfer controller 368 before initiating the next scalar transfer. Writing to scalar address register 1001, 1002 or scalar data register 1004, 1006 when the scalar done bit is not set causes indeterminate results.

Block transfer controller 368 processes scalar transfers from active execution units 360a-n within image processor 300, beginning with execution unit 360a. For outputs, block transfer controller 368 fetches the scalar address and scalar data from the first active execution unit 360a-n and executes a write to global memory 366 through memory interface 370. For inputs, block transfer controller 368 only fetches the scalar address, executes a read of global memory 366 and loads the data which it read from global memory 366 into the scalar data register.

After processing execution unit 3601a, if execution unit 360a is active, block transfer controller 368 proceeds to the remaining active execution units 360b-n until all active execution units 360a-n are serviced. After the first set of scalar transfers is completed, the first scalar done bit is set by block transfer controller 368. When finished with the first set of scalar transfers, block transfer controller 368 processes the second set in the same sequence. When the second set of scalar transfers is completed, block transfer controller 368 sets the second scalar done bit. Each execution datapath 358a-n of single-instruction multiple-data image processor 300 may have up to two sets of scalar transfers pending at same time within execution datapaths 358a-n. Image processor 300 cannot initiate a third scalar transfer before the first transfer is completed.

The two scalar done bits are located in the condition code register of each execution datapath 358a-n. These two scalar done bits are determined by block transfer controller 368, one for each set of scalar transfers, as previously described. The scalar done bits are cleared when execution units 360a-n again initiate scalar transfers in accordance with instructions applied to execution units 360a-n by sequence controller 352 by way of instruction broadcast line 356. To generate the correct results for scalar transfers, it is therefore necessary to check the scalar done bits before initiating the scalar transfer.

As previously described, the scalar transfer has lower access priority than the, instruction fetch within single-instruction multiple-data image processor 300 of the present invention. Block transfer controller 368 of image processor 300 therefore suspends any scalar transfer operation in progress when an instruction fetch is requested. To service the instruction fetch, block transfer controller 368 and memory interface 370 finish the outstanding read or write access of the scalar transfer being suspended. The higher priority instruction fetch is serviced by block transfer controller 368. The suspended scalar transfer is then completed.

Block transfer controller 368 supports scalar internal broadcast transfer. When the microcode writes to the internal broadcast transfer registers the broadcast scalar transfer is initiated. The data in the scalar data register is broadcasted to other scalar data registers. The execution mask bit of all but one of the n individual execution units 360a-n is set in order to initiate a scalar internal broadcast transfer within single-instruction multiple-data image processor 300. The data register of the single unmasked execution unit 360a-n is the source of the request for the scalar internal broadcast transfer. The data registers of the remaining masked execution units 60a-n are destinations for the scalar internal broadcast transfer. The scalar broadcast only supports word data transfer. The scalar address registers are ignored in the scalar broadcast transfer.

Block transfer controller 368 also supports instruction fetch for single-instruction multiple-data image processor 300. When the instruction cache of single-instruction multiple-data image processor 300 misses within image processor 300, sequence controller 352 is halted. Following this, block transfer controller 368 fetches the external instruction block address from sequence controller 352. Block transfer controller 368 uses the block address to read an instruction block from memory and load it into instruction random access memory 380 located in controller 352. After the instructions are loaded, sequence controller 352 resumes operation and applies instructions to execution datapaths 358a-n.

Referring now to FIG. 10, there is shown a more detailed block diagram representation of statistical decoder input channel 372 of single-instruction multiple-data image processor 300 of the present invention. Statistical decoder input channel 372 of image processor 300 is a specialized input channel having input channel processor 1116 that reads a variable-length bit sequence from global memory 366 and converts it into a fixed-length bit sequence that is read by execution datapath 358a only.

Because input channel 372 or statistical decoder 372 is a specialized hardware channel having its own input channel processor 1116 it may function as a semi-autonomous unit capable of performing part of the decoding process. This removes some of the burden of decoding input data from execution units 360a-n and eliminates the need for some instruction coding. Input channel processor 1116, execution units 360a-n, and transmission output line 1112 are all formed on a single integrated circuit chip.

Statistical decoder channel. 372 functions by having input channel processor 1116 prefetch and decode data. This function is performed when the program executing on executing units 360a-n provides the address of the data to channel processor 1116 and instructs it to begin. It will be understood that the decoding performed by input channel processor 1116 of statistical decoder input channel 372 may take place simultaneously with execution of program instructions by execution units 360a-n. The program executing on execution units 360a-n of image processor 300 later reads and processes the data received from statistical decoder 372 by way of transmission line 1116.

During image compression by an image processor such as single-instruction multiple-data image processor 300, as well as during other applications such as text compression, certain values within the data being compressed occur more frequently than others. One way to compress data of this nature is to use fewer bits to encode more frequently occurring values and more bits to encode less frequently occurring values. This type of encoding results in a variable-length sequence in which the length of a code may range, for example, from one bit to sixteen bits. It will be understood by those skilled in the art that a code is a group of bits used to encode a single value.

Statistical decoder input channel input channel 372 includes get₋₋ next_(--b) 8 -bits logic block 1104 and memory 1108. Memory 1108 may store a decoding tree such as a conventional Huffman coding tree. Decoder 372 may, for example, decode up to eight bits in code length. Input channel processor 1116 of statistical decoder 372 determines the next eight parallel bits of a bitstream applied to decoder 372 by way of input line 1102 and uses them as an address on address line 1106 to access memory 1108. Using the address information in this way, statistical decoder 372 obtains a decoded value from memory 1108. This decoded memory output value, which may have a twenty bit fore, at, appears on memory output line 1110.

In the preferred embodiment, four bits of the format stored in memory 1108 may be used to indicate the size of the bits to be shifted in the next cycle, one bit may provide a flag for indicating when the decoding is completed, and fifteen bits may represent the value returned to the microcode executing within execution datapaths 358a-n. Feedback loop 1114 feeds the four bits of shift size back to get₋₋ next₋₋ 8-bit logic block 1104. In the preferred embodiment the sixteen bit output value appears on decoder output line 1112.

Statistical decoder input channel 372 of single-instruction multiple-data processor 300 may operate in one of two modes, a native mode and a compatible mode. In the native mode, statistical decoder 372 may be used for Huffman decoding. In this mode of statistical decoder 372, decoder 372 decodes data provided by a conventional Huffman coding scheme in a manner well known to those skilled in the art. The Huffman coding scheme is described in Huffman, D. A., "A Method for the Construction of Minimum Redundancy Codes," Proc. Inst. Electr. Radio Eng 40, 9, Sep., 1952, pages 1098-1101.

When in the compatible mode, statistical decoder 372 of image processor 300 may be used for the statistical decoding of data encoded by coding schemes other than a conventional Huffman encoding scheme in accordance with the operation of compatible image processors (not shown). Operation of statistical decoder 372 in the native mode or in the conditional mode may be selected by writing an appropriate value into a control register (not shown) within sequence controller 352. It is possible to use statistical decoder 372 in either of these two modes, whether image processor 300 is running in its own native mode or in a compatible mode provided for processing of data in accordance with a compatible image processor (not shown).

Referring now to FIG. 11, there is shown binary decoding tree 1200. Binary decoding tree 1200 represents a coding scheme such as a conventional Huffman coding scheme. Binary decoding tree 1200 is used by statistical decoder 372 to convert variable-length bit input sequences into fixed length bit sequences within single-instruction multiple-data image processor 300. Memory 1108 of statistical decoder 372 may store binary decoding tree 1200 for decoding variable length coded data within single-instruction multiple-data image processor 300 of the present invention. Access to values determined in accordance with binary decoding tree 1200 and stored within memory 1108 is obtained by way of address line 1106 as previously described.

Decoding by means of binary decoding tree 1200 begins at root node 1202. When decoding is performed bit-by-bit, statistical decoder 372 tests the next bit from the bitstream of decoder input line 1102 to determine whether the next bit has the value one or the value zero. Statistical decoder 372 takes right branch 1204 of binary decoding tree 1200 if the tested bit is one. Statistical decoder 372 takes left branch 1206, if the tested bit is zero.

There is a decode₋₋ completed flag associated with each node of binary decoding tree 1200. The decode₋₋ completed flag indicates whether the decoding of a bit sequence is completed at the node. If the decode₋₋ completed flag for a node is set, statistical decoder 372 stops decoding, and reports the value stored in the node. Then, the next decoding starts from root node 1202. If the flag is not set, statistical decoder 372 tests the next bit of the input bitstream and continues from its current node.

In this example, decoding is performed by statistical decoder 372 bit-by-bit while using binary decoding tree 1200. However, statistical decoder 372 of image processor 300 may also decode several bits of the input bitstream at a time.

Referring now to FIG. 12, there is shown block transfer controller priority algorithm 1300 of the present invention. As previously described, execution of block transfer controller priority algorithm 1300 proceeds from Group I wherein local priority 1310 is executed. Execution of Group I as shown in block 1302 is then followed by execution of Group II as shown in block 1304. Within Group II, local priority 1312 is executed.

Following execution of Group II in block 1304, execution proceeds to block 1306 wherein Group I is again executed. Within block 1306 local priority 1314 is executed. It will be understood by those skilled in the art that local priority 1314 may be substantially similar to local priority 1310. Execution of block transfer controller priority algorithm 1300 then proceeds to Group III as shown in block 1308. Within block 1308, local priority 1316 is executed. Following execution of local priority 1316 within Group III, execution of block transfer controller priority algorithm 1300 returns to block 1302.

Referring now to FIG. 13, there is shown a block diagram representation of local priority 1310 for prioritizing Group I transfers in accordance with block transfer controller priority algorithm 1300. Local priority 1310 will be understood to be substantially similar to local priority 1314, and is adapted to provide specified priorities between the different types of transfers within Group I. When execution of priority algorithm 1300 proceeds to local priority 1310, a determination is made in decision 1320 whether any VRAM devices require service. If it is determined in decision 1320 that a VRAM device must be serviced, the VRAM transfer is performed as shown in block 1326 and execution proceeds to return loop 1332.

If no VRAM devices require service, as determined in decision 1320, a determination is made in decision 1322 whether any audio devices require service. If an audio device requires service it is served in block 1328 and execution proceeds to return loop 1332. Finally, within local priority 1310, a determination is made whether memory refresh is required in decision 1324. If memory refresh is required, it is performed in block 1330 and execution proceeds to return loop 1332.

Referring now to FIG. 14, there is shown a block diagram representation of local priority 1312 for prioritizing Group II transfers in accordance with block transfer controller priority algorithm 1300. Local priority 1312 is adapted to provide specified priorities between the different types of transfers within Group II. When execution of priority algorithm 1300 proceeds to local priority 1312, a determination is made in decision 1340 whether any system scaler read/writes are required. If it is determined in decision 1340 that a scalar read/writes is required, it is performed as shown in block 1346 and execution proceeds to return loop 1354. Override logic 1356 is provided in return loop 1354 in order to permit continued service of requests by local logic 1312 if no Group I or Group II transfers are pending.

If no scalar transfer is required, as determined in decision 1340, a determination is made in decision 1342 whether any system burst read/writes are required. If so, it is served in block 1348 and execution proceeds to return loop 1354. Transfer limiting block 1350 limits the number of transfers in block 1348 to sixteen as previously described. Finally, within local priority 1312, a determination is made whether two-dimensional transfers are requested as shown in decision 1344. If two-dimensional direct memory access transfers are required, it is performed in block 1350 and execution proceeds to return loop 1354.

Referring now to FIG. 15, there is shown a block diagram representation of local priority 1316 for prioritizing Group III transfers in accordance with block transfer controller priority algorithm 1300. Local priority 1316 is adapted to provide specified priorities between the different types of transfers within Group III. When execution of priority algorithm 1300 proceeds to local priority 1316, a determination is made in decision 1360 whether a cache line miss has occurred. If it is determined in decision 1360 that a cache line miss has occurred, it is serviced as shown in block 1366 and execution proceeds to return loop 1372.

If no a cache line miss has occurred, as determined in decision 1360, a determination is made in decision 1362 whether any scalar transfers are required. If a scalar transfer is required it is performed in block 1368 and execution proceeds to return loop 1372. Finally, within local priority 1316, a determination is made whether a block transfer is required in decision 1364. If a block transfer is required, it is performed in block 1370 and execution proceeds to return loop 1372.

As previously described the purpose of return override logic 1356 is to prevent execution of block transfer controller priority algorithm 1300 from returning from either local priority 1312 or local priority 1316 if no other requests are awaiting service. It will be understood by those skilled in the art that it is advantageous to avoid polling Groups I and III if execution in Group II is complete when determining whether to return from Group II in accordance with override logic 1356. Likewise it is advantageous to avoid polling Groups I and II if execution of Group III is complete to determine whether to return from Group II in accordance with override logic 1356. Thus, priority override logic 1356 may be provided by means of hardware rather than software in the preferred embodiment of block memory transfer controller priority algorithm 1300.

Referring now to FIG. 16, there is shown a more detailed block diagram representation of transfer limiting algorithm 1350. Within Group III and when dealing with system burst read/writes or two-dimensional requests in Group II, it is advantageous to limit the number of requests which may be serviced at a time to sixteen as previously described. Therefore, when a transfer is performed as shown in block 1380 of transfer limiting algorithm 1350, a determination is made in decision 1382 whether any further transfers have been requested. If no further transfers are requested, execution may continue. However, if more transfers are awaiting service within Group II or Group III, as determined in decision 1382, a determination is made in decision 1384 whether a total of sixteen transfers have been performed. If not, execution may proceed back to transfer block 1380 and another transfer may be performed. However, if a determination is made in decision 1384 that sixteen transfers have been performed, execution returns to return loop 1332.

It will be understood that the system scalar transfers within Group II are a special case wherein only one single transfer is performed by definition. Thus, it will be understood by those skilled in the art that algorithm 1350 need not be executed upon an affirmative determination within decision 1346.

It will be understood that various changes in the details, materials and arrangements of the parts which have been described and illustrated in order to explain the nature of this invention may be made by those skilled in the art without departing from the principle and scope of the invention as expressed in the following claims. 

I claim:
 1. A single-instruction multiple-data processing system for implementing prioritized input/output data handling, the system comprising:(a) a plurality of system components each requesting at least one data transfer via an input/output data stream of the system to provide a plurality of data transfer requests, said each data transfer having a data transfer type of a plurality of data transfer types, and each of said data transfer types having an associated bandwidth requirement; (b) means for setting a first, second, or third priority level for each data transfer type of the plurality of data transfer types in accordance with the bandwidth requirement of each data transfer type, wherein the first priority level data transfers are data transfers having relatively low bandwidth requirements, the second priority level data transfers are data transfers having bursty bandwidth requirements, and the third priority level data transfers are data transfers having relatively high bandwidth requirements; (c) means for servicing the plurality of data transfer requests by providing for transfer of data via the input/output data stream for selected data transfer requests of the plurality of data transfer requests in the order: first priority level, second priority level, first priority level, third priority level; and (d) means for successively repeating the servicing of servicing means (c) for unsatisfied data transfer requests of the plurality of data transfer requests.
 2. The system of claim 1, wherein:the setting means further comprises means for setting a relative local priority level for each data transfer type within a given priority level; and the servicing means further comprises means for servicing data transfer requests of the same priority level in accordance with the relative local priority levels of the data transfer requests of the same priority level.
 3. A system for implementing prioritized input/output data handling, comprising:(a) a plurality of system components each requesting at least one data transfer via an input/output data stream of the system to provide a plurality of pending data transfer requests, said each data transfer having a data transfer type of a plurality of data transfer types, each of said data transfer types having an associated bandwidth requirement; (b) means for setting a first, second, or third priority level for each of said data transfer types of the plurality of data transfer types in accordance with the bandwidth requirement of each data transfer type, wherein the first priority level data transfers are data transfers having relatively bandwidth requirements, the second priority level data transfers are data transfers having bursty bandwidth requirements, and the third priority level data transfers are data transfers having relatively high bandwidth requirements; (c) means for polling all pending first priority data transfer requests and servicing a selected first priority data transfer request of the pending first priority data transfer requests, wherein servicing a data transfer request comprises providing for transfer of data via the input/output data stream; (d) means for polling all pending second priority data transfer requests and servicing a selected second priority data transfer request of the pending second priority data transfer requests; (e) means for polling all pending first priority data transfer requests and servicing a second selected first priority data transfer request of the pending first priority data transfer requests; (f) means for polling all pending third priority data transfer requests and servicing a selected third priority data transfer request of the pending second priority data transfer requests; and (g) means for successively repeating the polling and servicing of means (c)-(f).
 4. The system of claim 3, wherein:the setting means further comprises means for setting a relative local priority level for each data transfer type within a given priority level; and pending data transfer requests are selected for servicing by means for polling in (c)-(f) in accordance with the relative local priority levels of the data transfer requests of the same priority level.
 5. A method for implementing prioritized input/output data handling in a single-instruction multiple-data processing system having a plurality of system components each requesting at least one clam transfer via an input/output data stream of the system to provide a plurality of data transfer requests, said each data transfer having a data transfer type of a plurality of data transfer types, and each of said data transfer types having an associated bandwidth requirement, the method comprising the steps of:(a) setting a first, second, or third priority level for each of said data transfer types of the plurality of data transfer types in accordance with the bandwidth requirement of each data transfer type, wherein the first priority level data transfers are data transfer having relatively low bandwidth requirements, the second priority level data transfers are data transfers having bursty bandwidth requirements, third priority level data transfers are data transfers having relatively high bandwidth requirements; (b) servicing the plurality of data transfer requests by providing for transfer of data via the input/output data stream for selected data transfer requests of the plurality of data transfer requests in the order: first priority level, second priority level, first priority level, third priority level; and (c) successively repeating the servicing of step (b) for unsatisfied data transfer requests of the plurality of data transfer requests.
 6. The method of claim 5, wherein:step (a) further comprises the step of setting a relative local priority level for each data transfer type within a given priority level; and step (b) further comprises the step of servicing data transfer requests of a same priority level in accordance with the relative local priority levels of the data transfer requests of the same priority level. 